- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3
fully configurable elasticsearch solution #428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
1b94932    to
    4550455      
    Compare
  
    | /run pipeline | 
4550455    to
    c91a000      
    Compare
  
    | /run pipeline | 
    
      
        1 similar comment
      
    
  
    | /run pipeline | 
1afeca2    to
    3cde97d      
    Compare
  
    | /run pipeline | 
5018bdc    to
    e4798d0      
    Compare
  
    | /run pipeline | 
a9b6986    to
    4a7d4f2      
    Compare
  
    | /run pipeline | 
    
      
        1 similar comment
      
    
  
    | /run pipeline | 
07c0ac4    to
    d694ebb      
    Compare
  
    | /run pipeline | 
d694ebb    to
    3947525      
    Compare
  
    | /run pipeline | 
    
      
        2 similar comments
      
    
  
    | /run pipeline | 
| /run pipeline | 
b1431d5    to
    78d311d      
    Compare
  
    | /run pipeline | 
    
      
        1 similar comment
      
    
  
    | /run pipeline | 
094e3fc    to
    ffa72c9      
    Compare
  
    | /run pipeline | 
| } | ||
|  | ||
| variable "skip_es_kms_auth_policy" { | ||
| variable "skip_elasticsearch_kms_auth_policy" { | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check skip_redis_kms_auth_policy in redis, which description is correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the elasticsearch description is more accurate
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, we need to change in redis
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes made in fully-configurable, should be added to security-enforced as well
1d86fe0    to
    caa7b10      
    Compare
  
    caa7b10    to
    1e6e255      
    Compare
  
    | /run pipeline | 
    
      
        1 similar comment
      
    
  
    | /run pipeline | 
| /run pipeline | 
| /run pipeline | 
    
      
        1 similar comment
      
    
  
    | /run pipeline | 
1779b7d    to
    5df79da      
    Compare
  
    | /run pipeline | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check input "users" in security DA as well and sync with redis
auto_scaling needs #autoscaling in a link (security)
| } | ||
|  | ||
| variable "skip_es_kms_auth_policy" { | ||
| variable "skip_elasticsearch_kms_auth_policy" { | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, we need to change in redis
| /run pipeline | 
| /run pipeline | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
| 🎉 This PR is included in version 2.0.0 🎉 The release is available on: 
 Your semantic-release bot 📦🚀 | 
BREAKING CHANGE: There is no supported upgrade path from `standard` to the new `Fully configurable` or `Security-enforced` DA variations
For issue - https://github.ibm.com/GoldenEye/issues/issues/12892
Description
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers